Skip to content

fix(deploy): the site reserves 128Mi, so its update fits next to the API in the quota - #9

Merged
kenzycodex merged 2 commits into
mainfrom
fix/quota-room
Nov 11, 2026
Merged

kenzycodex merged 2 commits into
mainfrom
fix/quota-room

Conversation

@kenzycodex

@kenzycodex kenzycodex commented Nov 11, 2026 •

Copy link
Copy Markdown
Owner

Why

After the last deploy the API pod was refused: exceeded quota: team-quota, requested: requests.memory=256Mi, used: requests.memory=768Mi. While the site updates, two of its pods run side by side, and at 256Mi each they plus the API filled the namespace's 768Mi.

What changes

  • deploy/forge/app.yaml: the site reserves 128Mi instead of 256Mi (its limit stays 512Mi). The API keeps 256Mi. During a site update: 256 + 128 + 128 = 512 of 768.
  • docs/DEPLOY-FORGE.md: a troubleshooting row for a missing API pod after an update, and how to recover.

Checked

  • The manifest parses and lists the two deployments and two services with the new requests.

@kenzycodex
kenzycodex merged commit 6652d88 into main Nov 11, 2026
1 of 5 checks passed
@kenzycodex
kenzycodex deleted the fix/quota-room branch November 11, 2026 13:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant